Convert resident tag to srkw tag - #596

Ran this locally with a few unreviewed candidates seeded the way PODS-AI writes them, tags pre-populated with resident. The conversion itself works: the card comes up as srkw;orca;whale and clicking Yes adds nothing extra, so the #595 mix is gone. Typing resident by hand still sticks, so the escape hatch in the comment works too.

Two findings:

1. AddTag("srkw") still carries the side effect from Make managing tags easier when moderating candidates #561 that flips the SRKW radio to Yes. On the single detection page a resident candidate now loads with Yes preselected and Submit enabled before anyone has listened. On the candidates page the same record shows the srkw chips with nothing selected, because a later OnParametersSet pass resets Found while the tags stay converted. The two pages disagree on the same data, and the queue lands in the tag-without-radio state Update SRKW radio when manually adding srkw tag #567 was about. Doing the translation on the tag string before the AddTag calls, or clearing Found after converting, would keep the radio untouched.

2. The new guard is case sensitive while the rest of the file compares tags with OrdinalIgnoreCase. A Resident slips through unconverted, and clicking Yes then gives Resident;srkw;orca;whale, the same mix as Moderator portal tags: SRKW vs resident #595. Detection.TagList.Contains("resident", StringComparer.OrdinalIgnoreCase) would line it up; RemoveTag already handles case itself. Might be theoretical if PODS-AI always writes lowercase.

One thing worth deciding rather than a finding: with srkw pre-filled, answering No leaves orca;whale on the record unless the moderator removes them by hand. Before this change a No left resident behind instead, so it's not worse, but if the intent is Dave Bain's "get rid of resident as a tag for now", dropping the tag without adding srkw would avoid both. Whichever way you go, I can retest quickly.

@kauereinbold updated, please re-review. Yes PODS-AI always uses "resident" lower case today, but I updated this to use case-insensitive anyway. Thanks for the review and testing!